System and method for zoning a distributed-architecture heating, ventilation and air conditioning network

ABSTRACT

The disclosure provides an HVAC data processing and communication network. In an embodiment, the network includes a first zone and a second zone. The first zone has a first demand unit and a first subnet controller configured to control an operation of the first demand unit via a data bus. The second zone has a second demand unit and a second subnet controller configured to control an operation of the second demand unit via the data bus. The second subnet controller is further configured to communicate with the first subnet controller via the data bus.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application Ser.No. 61/167,135, filed by Grohman, et al., on Apr. 6, 2009, entitled“Comprehensive HVAC Control System”, and is a continuation-in-partapplication of application Ser. No. 12/258,659, filed by Grohman on Oct.27, 2008, entitled “Apparatus and Method for Controlling anEnvironmental Conditioning Unit,” both of which are commonly assignedwith this application and incorporated herein by reference. Thisapplication is also related to the following U.S. patent applications,which are filed on even date herewith, commonly assigned with thisapplication and incorporated herein by reference:

Ser. No. Inventors Title [Attorney Grohman, et “Alarm and DiagnosticsSystem and Method Docket al. for a Distributed-Architecture Heating, No.Ventilation and Air Conditioning 080161] Network” [Attorney Wallaert,“Flush Wall Mount Controller and In-Set Docket et al. Mounting Plate fora Heating, No. Ventilation and Air Conditioning System” 070064][Attorney Thorson, et “System and Method of Use for a User Docket al.Interface Dashboard of a Heating, No. Ventilation and Air Conditioning070027] Network” [Attorney Grohman “Device Abstraction System and MethodDocket for a Distributed-Architecture Heating, No. Ventilation and AirConditioning 070016] Network” [Attorney Grohman, et “CommunicationProtocol System and Docket al. Method for a Distributed-Architecture No.Heating, Ventilation and Air 070079] Conditioning Network” [AttorneyHadzidedic “Memory Recovery Scheme and Data Docket Structure in aHeating, Ventilation and No. Air Conditioning Network” 080151] [AttorneyGrohman “System Recovery in a Heating, Docket Ventilation and AirConditioning No. Network” 080173] [Attorney Grohman, et “System andMethod for Zoning a Docket al. Distributed-Architecture Heating, No.Ventilation and Air Conditioning 080131] Network” [Attorney Grohman, et“Method of Controlling Equipment in a Docket al. Heating, Ventilationand Air No. Conditioning Network” 080163] [Attorney Grohman, et“Programming and Configuration in a Docket al. Heating, Ventilation andAir No. Conditioning Network” 080160] [Attorney Mirza, et “GeneralControl Techniques in a Docket al. Heating, Ventilation and Air No.Conditioning Network” 080146]

TECHNICAL FIELD

This application is directed, in general, to HVAC systems and, morespecifically, to a system and method for logical manipulation of systemfeatures.

BACKGROUND

Climate control systems, also referred to as HVAC systems (the two termswill be used herein interchangeably), are employed to regulate thetemperature of premises, such as a residence, office, store, warehouse,vehicle, trailer, or commercial or entertainment venue. The most basicclimate control systems either move air (typically by means of an airhandler having a fan or blower), heat air (typically by means of afurnace) or cool air (typically by means of a compressor-drivenrefrigerant loop). A thermostat is typically included in a conventionalclimate control system to provide some level of automatic temperaturecontrol. In its simplest form, a thermostat turns the climate controlsystem on or off as a function of a detected temperature. In a morecomplex form, the thermostat may take other factors, such as humidity ortime, into consideration. Still, however, the operation of a thermostatremains turning the climate control system on or off in an attempt tomaintain the temperature of the premises as close as possible to adesired set point temperature.

Climate control systems as described above have been in wide use sincethe middle of the twentieth century and have, to date, generallyprovided adequate temperature management.

SUMMARY

One aspect provides an HVAC data processing and communication network.In an embodiment, the network includes a first zone and a second zone.The first zone has a first demand unit and a first subnet controllerconfigured to control an operation of the first demand unit via a databus. The second zone has a second demand unit and a second subnetcontroller configured to control an operation of the second demand unitvia the data bus. The second subnet controller is further configured tocommunicate with the first subnet controller via the data bus.

Another aspect provides a method of manufacturing an HVAC dataprocessing and communication network. In an embodiment, the methodincludes configuring a first subnet controller and a second subnetcontroller. The first subnet controller is configured to control anoperation of a first demand unit in a first zone via a data bus. Thesecond subnet controller is configured to control an operation of asecond demand unit in a second zone via the data bus. The method furtherincludes configuring the first subnet controller to communicate with thesecond subnet controller via the data bus.

BRIEF DESCRIPTION

Reference is now made to the following descriptions taken in conjunctionwith the accompanying drawings, in which:

FIG. 1 is a high-level block diagram of an HVAC system according tovarious embodiments of the disclosure;

FIG. 2 is a high-level block diagram of one embodiment of an HVAC dataprocessing and communication network;

FIG. 3 is a block diagram of a local controller of the disclosure;

FIG. 4 is a block diagram of a networked HVAC system device of thedisclosure;

FIG. 5 illustrates an example grouping of devices in an HVAC system;

FIG. 6 illustrates two subnets in communication over a networkconnection;

FIGS. 7A and 8B illustrate a conditioned building with two HVAC zones;

FIG. 8 illustrates operating states of the active subnet controller;

FIG. 9 illustrates a user interface display with a user dashboard;

FIG. 10 is an embodiment of the disclosure illustrating navigationbetween screens of the user interface;

FIG. 11 is an embodiment of the disclosure illustrating a home screen ofthe user interface display;

FIG. 12 is an embodiment of the disclosure illustrating an indoorhumidity screen of the user interface display;

FIG. 13 is an embodiment of the disclosure illustrating an alert screenof the user interface display;

FIG. 14A is an embodiment of the disclosure illustrating navigation ofthe alert screen and associated subscreens of the user interfacedisplay;

FIG. 14B is an embodiment of the disclosure illustrating navigation of apop-up alert screen and associated subscreens of the user interfacedisplay;

FIG. 15 is an embodiment of the disclosure illustrating a help screen ofthe user interface display;

FIG. 16 is an embodiment of the disclosure illustrating navigation ofthe help screen and associated subscreens;

FIG. 17 is an embodiment of the disclosure illustrating an indoorsettings screen of the user interface display;

FIG. 18 is an embodiment of the disclosure illustrating navigation ofthe indoor settings screen and associated subscreens of the userinterface display;

FIG. 19 is an embodiment of the disclosure illustrating a program screenof the user interface display;

FIG. 20 is an embodiment of the disclosure illustrating navigation ofthe program screen and associated subscreens of the user interfacedisplay;

FIG. 21 is an embodiment of the disclosure illustrating a zones screenof the user interface display;

FIG. 22A is an embodiment of the disclosure illustrating navigation ofthe zones screen and associated subscreens of the user interfacedisplay;

FIG. 22B is an embodiment of the disclosure illustrating a zones detailscreen;

FIG. 23 is an embodiment of a whole-house override screen;

FIG. 24 is an embodiment of a method of navigating the whole-houseoverride screen and associated subscreens of the user interface display;

FIG. 25 is an embodiment of the disclosure illustrating navigation ofwhole-house program screen and associated subscreens of the userinterface display;

FIG. 26 illustrates a method of the disclosure of configuring an HVACsystem for zoned operation;

FIGS. 27-30 illustrates methods of the disclosure;

FIG. 31 illustrates an installer dashboard; and

FIG. 32 illustrates transitions between service screens.

DETAILED DESCRIPTION

As stated above, conventional climate control systems have been in wideuse since the middle of the twentieth century and have, to date,generally provided adequate temperature management. However, it has beenrealized that more sophisticated control and data acquisition andprocessing techniques may be developed and employed to improve theinstallation, operation and maintenance of climate control systems.

Described herein are various embodiments of an improved climate control,or HVAC, system in which at least multiple components thereofcommunicate with one another via a data bus. The communication allowsidentity, capability, status and operational data to be shared among thecomponents. In some embodiments, the communication also allows commandsto be given. As a result, the climate control system may be moreflexible in terms of the number of different premises in which it may beinstalled, may be easier for an installer to install and configure, maybe easier for a user to operate, may provide superior temperature and/orrelative humidity (RH) control, may be more energy efficient, may beeasier to diagnose, may require fewer, simpler repairs and may have alonger service life.

FIG. 1 is a high-level block diagram of a networked HVAC system,generally designated 100. The HVAC system 100 may be referred to hereinsimply as “system 100” for brevity. In one embodiment, the system 100 isconfigured to provide ventilation and therefore includes one or more airhandlers 110. In an alternative embodiment, the ventilation includes oneor more dampers 115 to control air flow through air ducts (not shown.)Such control may be used in various embodiments in which the system 100is a zoned system. In an alternative embodiment, the system 100 isconfigured to provide heating and therefore includes one or morefurnaces 120, typically associated with the one or more air handlers110. In an alternative embodiment, the system 100 is configured toprovide cooling and therefore includes one or more refrigerantevaporator coils 130, typically associated with the one or more airhandlers 110. Such embodiment of the system 100 also includes one ormore compressors 140 and associated condenser coils 142, which aretypically associated with one or more so-called “outdoor units” 144. Theone or more compressors 140 and associated condenser coils 142 aretypically connected to an associated evaporator coil 130 by arefrigerant line 146. In an alternative embodiment, the system 100 isconfigured to provide ventilation, heating and cooling, in which casethe one or more air handlers 110, furnaces 120 and evaporator coils 130are associated with one or more “indoor units” 148, e.g., basement orattic units that may also include an air handler.

For convenience in the following discussion, a demand unit 155 isrepresentative of the various units exemplified by the air handler 110,furnace 120, and compressor 140, and more generally includes an HVACcomponent that provides a service in response to control by the controlunit 150. The service may be, e.g., heating, cooling, humidification,dehumidification, or air circulation. A demand unit 155 may provide morethan one service, and if so, one service may be a primary service, andanother service may be an ancillary service. For example, for a heatingunit that also circulates air, the primary service may be heating, andthe ancillary service may be air circulation (e.g. by a blower).

The demand unit 155 may have a maximum service capacity associatedtherewith. For example, the furnace 120 may have a maximum heat output(often expressed in terms of British Thermal Units (BTU) or Joules), ora blower may have a maximum airflow capacity (often expressed in termsof cubic feet per minute (CFM) or cubic meters per minute (CMM)). Insome cases, the demand unit 155 may be configured to provide a primaryor ancillary service in staged portions. For example, blower may havetwo or more motor speeds, with a CFM value associated with each motorspeed.

One or more control units 150 control one or more of the one or more airhandlers 110, the one or more furnaces 120 and/or the one or morecompressors 140 to regulate the temperature of the premises, at leastapproximately. In various embodiments to be described, the one or moredisplays 170 provide additional functions such as operational,diagnostic and status message display and an attractive, visualinterface that allows an installer, user or repairman to perform actionswith respect to the system 100 more intuitively. Herein, the term“operator” will be used to refer collectively to any of the installer,the user and the repairman unless clarity is served by greaterspecificity.

One or more separate comfort sensors 160 may be associated with the oneor more control units 150 and may also optionally be associated with oneor more displays 170. The one or more comfort sensors 160 provideenvironmental data, e.g. temperature and/or humidity, to the one or morecontrol units 150. An individual comfort sensor 160 may be physicallylocated within a same enclosure or housing as the control unit 150, in amanner analogous with a conventional HVAC thermostat. In such cases, thecommonly housed comfort sensor 160 may be addressed independently.However, the one or more comfort sensors 160 may be located separatelyand physically remote from the one or more control units 150. Also, anindividual control unit 150 may be physically located within a sameenclosure or housing as a display 170, again analogously with aconventional HVAC thermostat. In such embodiments, the commonly housedcontrol unit 150 and display 170 may each be addressed independently.However, one or more of the displays 170 may be located within thesystem 100 separately from and/or physically remote to the control units150. The one or more displays 170 may include a screen such as a liquidcrystal or OLED display (not shown).

Although not shown in FIG. 1, the HVAC system 100 may include one ormore heat pumps in lieu of or in addition to the one or more furnaces120, and one or more compressors 140. One or more humidifiers ordehumidifiers may be employed to increase or decrease humidity. One ormore dampers may be used to modulate air flow through ducts (not shown).Air cleaners and lights may be used to reduce air pollution. Air qualitysensors may be used to determine overall air quality.

Finally, a data bus 180, which in the illustrated embodiment is a serialbus, couples the one or more air handlers 110, the one or more furnaces120, the one or more evaporator condenser coils 142 and compressors 140,the one or more control units 150, the one or more remote comfortsensors 160 and the one or more displays 170 such that data may becommunicated therebetween or thereamong. As will be understood, the databus 180 may be advantageously employed to convey one or more alarmmessages or one or more diagnostic messages. All or some parts of thedata bus 180 may be implemented as a wired or wireless network.

The data bus 180 in some embodiments is implemented using the Bosch CAN(Controller Area Network) specification, revision 2, and may besynonymously referred to herein as a residential serial bus (RSBus) 180.The data bus 180 provides communication between or among theaforementioned elements of the network 200. It should be understood thatthe use of the term “residential” is nonlimiting; the network 200 may beemployed in any premises whatsoever, fixed or mobile. Other embodimentsof the data bus 180 are also contemplated, including e.g., a wirelessbus, as mentioned previously, and 2-, 3- or 4-wire networks, includingIEEE-1394 (Firewire™, i.LINK™, Lynx™), Ethernet, Universal Serial Bus(e.g., USB 1.x, 2.x, 3.x), or similar standards. In wirelessembodiments, the data bus 180 may be implemented, e.g., usingBluetooth™, Zibgee or a similar wireless standard.

FIG. 2 is a high-level block diagram of one embodiment of an HVAC dataprocessing and communication network 200 that may be employed in theHVAC system 100 of FIG. 1. One or more air handler controllers (AHCs)210 may be associated with the one or more air handlers 110 of FIG. 1.One or more integrated furnace controllers (IFCs) 220 may be associatedwith the one or more furnaces 120. One or more damper controller modules215, also referred to herein as a zone controller module 215, may beassociated with the one or more dampers 115. One or more unitarycontrollers 225 may be associated with one or more evaporator coils 130and one or more condenser coils 142 and compressors 140 of FIG. 1. Thenetwork 200 includes an active subnet controller (aSC) 230 a and aninactive subnet controller (iSC) 230 i. The aSC 230 a may act as anetwork controller of the system 100. The aSC 230 a is responsible forconfiguring and monitoring the system 100 and for implementation ofheating, cooling, humidification, dehumidification, air quality,ventilation or any other functional algorithms therein. Two or more aSCs230 a may also be employed to divide the network 200 into subnetworks,or subnets, simplifying network configuration, communication andcontrol. Each subnet typically contains one indoor unit, one outdoorunit, a number of different accessories including humidifier,dehumidifier, electronic air cleaner, filter, etc., and a number ofcomfort sensors, subnet controllers and user interfaces. The iSC 230 iis a subnet controller that does not actively control the network 200.In some embodiments, the iSC 230 i listens to all messages broadcastover the data bus 180, and updates its internal memory to match that ofthe aSC 230 a. In this manner, the iSC 230 i may backup parametersstored by the aSC 230 a, and may be used as an active subnet controllerif the aSC 230 a malfunctions. Typically there is only one aSC 230 a ina subnet, but there may be multiple iSCs therein, or no iSC at all.Herein, where the distinction between an active or a passive SC is notgermane the subnet controller is referred to generally as an SC 230.

A user interface (UI) 240 provides a means by which an operator maycommunicate with the remainder of the network 200. In an alternativeembodiment, a user interface/gateway (UI/G) 250 provides a means bywhich a remote operator or remote equipment may communicate with theremainder of the network 200. Such a remote operator or equipment isreferred to generally as a remote entity. A comfort sensor interface260, referred to herein interchangeably as a comfort sensor (CS) 260,may provide an interface between the data bus 180 and each of the one ormore comfort sensors 160. The comfort sensor 260 may provide the aSC 230a with current information about environmental conditions inside of theconditioned space, such as temperature, humidity and air quality.

For ease of description, any of the networked components of the HVACsystem 100, e.g., the air handler 110, the damper 115, the furnace 120,the outdoor unit 144, the control unit 150, the comfort sensor 160, thedisplay 170, may be described in the following discussion as having alocal controller 290. The local controller 290 may be configured toprovide a physical interface to the data bus 180 and to provide variousfunctionality related to network communication. The SC 230 may beregarded as a special case of the local controller 290, in which the SC230 has additional functionality enabling it to control operation of thevarious networked components, to manage aspects of communication amongthe networked components, or to arbitrate conflicting requests fornetwork services among these components. While the local controller 290is illustrated as a stand-alone networked entity in FIG. 2, it istypically physically associated with one of the networked componentsillustrated in FIG. 1.

FIG. 3 illustrates a high-level block diagram of the local controller290. The local controller 290 includes a physical layer interface (PLI)310, a non-volatile memory (NVM) 320, a RAM 330, a communication module340 and a functional block 350 that may be specific to the demand unit155, e.g., with which the local controller 290 is associated. The PLI310 provides an interface between a data network, e.g., the data bus180, and the remaining components of the local controller 290. Thecommunication module 340 is configured to broadcast and receive messagesover the data network via the PLI 310. The functional block 350 mayinclude one or more of various components, including without limitationa microprocessor, a state machine, volatile and nonvolatile memory, apower transistor, a monochrome or color display, a touch panel, abutton, a keypad and a backup battery. The local controller 290 may beassociated with a demand unit 155, and may provide control thereof viathe functional block 350, e.g. The NVM 320 provides local persistentstorage of certain data, such as various configuration parameters, asdescribed further below. The RAM 330 may provide local storage of valuesthat do not need to be retained when the local controller 290 isdisconnected from power, such as results from calculations performed bycontrol algorithms. Use of the RAM 330 advantageously reduces use of theNVM cells that may degrade with write cycles.

In some embodiments, the data bus 180 is implemented over a 4-wirecable, in which the individual conductors are assigned as follows:

R—the “hot”—a voltage source, 24 VAC, e.g.

C—the “common”—a return to the voltage source.

i+—RSBus High connection.

i−—RSBus Low connection.

The disclosure recognizes that various innovative system managementsolutions are needed to implement a flexible, distributed-architectureHVAC system, such as the system 100. More specifically, cooperativeoperation of devices in the system 100, such as the air handler 110,outdoor unit 144, or UI 240 is improved by various embodiments presentedherein. More specifically still, embodiments are presented of zoning ofa distributed architecture or networked HVAC system than providesimplified installation and operation relative to a conventional HVACsystem.

FIG. 4 illustrates a device 410 according to the disclosure. Thefollowing description pertains to the HVAC data processing andcommunication network 200 that is made up of a number of system devices410 operating cooperatively to provide HVAC functions. Herein after thesystem device 410 is referred to more briefly as the device 410 withoutany loss of generality. The term “device” applies to any component ofthe system 100 that is configured to communicate with other componentsof the system 100 over a wired or wireless network. Thus, the device 410may be, e.g., the air handler 110 in combination with its AHC 210, orthe furnace 120 in combination with its IFC 220. This discussion mayrefer to a generic device 410 or to a device 410 with a specific recitedfunction as appropriate. An appropriate signaling protocol may be usedto govern communication of one device with another device. While thefunction of various devices 410 in the network 200 may differ, eachdevice 410 shares a common architecture for interfacing with otherdevices, e.g. the local controller 290 appropriately configured for theHVAC component 420 with which the local controller 290 is associated.The microprocessor or state machine in the functional block 350 mayoperate to perform any task for which the device 410 is responsible,including, without limitation, sending and responding to messages viathe data bus 180, controlling a motor or actuator, or performingcalculations.

In various embodiments, signaling between devices 410 relies onmessages. Messages are data strings that convey information from onedevice 410 to another device 410. The purpose of various substrings orbits in the messages may vary depending on the context of the message.Generally, specifics regarding message protocols are beyond the scope ofthe present description. However, aspects of messages and messaging aredescribed when needed to provide context for the various embodimentsdescribed herein.

FIG. 5 illustrates an embodiment of the disclosure of a network of thedisclosure generally designated 500. The network 500 includes an aSC510, a user interface 520, a comfort sensor 530 and a furnace 540configured to communicate over a data bus 550. In some embodiments thesedevices form a minimum HVAC network. In addition, the network 500 isillustrated as including an outdoor unit 560, an outdoor sensor 570, anda gateway 580. The furnace 540 and outdoor unit 560 are provided by wayof example only and not limited to any particular demand units. The aSC510 is configured to control the furnace 540 and the outdoor unit 560using, e.g., command messages sent via the data bus 550. The aSC 510receives environmental data, e.g. temperature and/or humidity, from thecomfort sensor 530, the furnace 540 via a local temperature sensor, theoutdoor sensor 570 and the outdoor unit 560. The data may be transmittedover the data bus 550 by way of messages formatted for this purpose. Theuser interface 520 may include a display and input means to communicateinformation to, and accept input from, an operator of the network 500.The display and input means may be, e.g., a touch-sensitive displayscreen, though embodiments of the disclosure are not limited to anyparticular method of display and input.

The aSC 510, comfort sensor 530 and user interface 520 may optionally bephysically located within a control unit 590. The control unit 590provides a convenient terminal to the operator to effect operatorcontrol of the system 100. In this sense, the control unit is similar tothe thermostat used in conventional HVAC systems. However, the controlunit 590 may only include the user interface 520, with the aSC 510 andcomfort sensor 530 remotely located from the control unit 590.

As described previously, the aSC 510 may control HVAC functionality,store configurations, and assign addresses during system autoconfiguration. The user interface 520 provides a communication interfaceto provide information to and receive commands from a user. The comfortsensor 530 may measure one or more environmental attributes that affectuser comfort, e.g., ambient temperature, RH and pressure. The threelogical devices 510, 520, 530 each send and receive messages over thedata bus 550 to other devices attached thereto, and have their ownaddresses on the network 500. In many cases, this design featurefacilitates future system expansion and allows for seamless addition ofmultiple sensors or user interfaces on the same subnet. The aSC 510 maybe upgraded, e.g., via a firmware revision. The aSC 510 may also beconfigured to release control of the network 500 and effectively switchoff should another SC present on the data bus 550 request it.

Configuring the control unit 590 as logical blocks advantageouslyprovides flexibility in the configuration of the network 500. Systemcontrol functions provided by a subnet controller may be placed in anydesired device, in this example the control unit 590. The location ofthese functions therein need not affect other aspects of the network500. This abstraction provides for seamless upgrades to the network 500and ensures a high degree of backward compatibility of the localcontrollers 290 present in the network. The approach provides forcentralized control of the system, without sacrificing flexibility orincurring large system upgrade costs.

For example, the use of the logical aSC 510 provides a flexible means ofincluding control units on a same network in a same conditioned space.The system, e.g., the system 100, may be easily expanded. The systemretains backward compatibility, meaning the network 500 may be updatedwith a completely new type of equipment without the need to reconfigurethe system, other than substituting a new control unit 590, e.g.Moreover, the functions provided by the subnet controller may belogically placed in any physical device, not just the control unit 590.Thus, the manufacturer has greater flexibility in selecting devices,e.g., control units or UIs, from various suppliers.

In various embodiments, each individual subnet, e.g., the network 500,is configured to be wired as a star network, with all connections to thelocal controller 290 tied at the furnace 120 or the air handler 110.Thus, each indoor unit, e.g., the furnace 120, may include threeseparate connectors configured to accept a connection to the data bus180. Two connectors may be 4-pin connectors: one 4-pin connector may bededicated for connecting to an outdoor unit, and one may be used toconnect to equipment other than the outdoor unit. The third connectormay be a 2-pin connector configured to connect the subnet of which theindoor unit is a member to other subnets via the i+/i− signals. Asdescribed previously, a 24 VAC transformer associated with the furnace120 or air handler 110 may provide power to the local controllers 290within the local subnet via, e.g., the R and C lines. The C line may belocally grounded.

FIG. 6 illustrates a detailed connection diagram of components of anetwork 600 according to one embodiment of the disclosure. The network600 includes a zone 605 and a zone 610. The zones 605, 610 areillustrated without limitation as being configured as subnets 615, 620,respectively. The subnet 615 includes an air conditioning (AC) unit 630,a UI/G 640, an outside sensor (OS) 650, a control unit 660, and afurnace 670. The control unit 660 includes an SC 662, a UI 664 and acomfort sensor 666, each of which is independently addressable via adata bus 180 a. The subnet 620 includes a control unit 680, a heat pump690 and a furnace 695. The control unit 680 houses an SC 682, a UI 684and a comfort sensor 686, each of which is independently addressable viaa data bus 180 b. In various embodiments and in the illustratedembodiment each individual subnet, e.g., the subnets 615, 620 are eachconfigured to be wired as a star network, with connections to alldevices therein made at a furnace an air handler associated with thatsubnet. Thus, e.g., each of the devices 630, 640, 650, 660 is connectedto the data bus 180 a at the furnace 670. Similarly, each device 680,690 is connected to the subnet 620 at the furnace 695. Each furnace 670,695, generally representative of the indoor unit 148, may include aconnection block configured to accept a connection to the RSBus 180. Forexample, two terminals of the connection block may be 4-pin connectors.In one embodiment, one 4-pin connector is dedicated to connecting to anoutdoor unit, for example the connection from the furnace 670 to the ACunit 630. Another 4-pin connector is used to connect to equipment otherthan the outdoor unit, e.g., from the furnace 670 to the UI/G 640, theOS 650, and the control unit 660. A third connector may be a 2-pinconnector configured to connect one subnet to another subnet. In thenetwork 600, e.g., the subnet 615 is connected to the subnet 620 via awire pair 698 that carries the i+/i− signals of the serial bus. Asdescribed previously with respect to the furnace 120, a transformerlocated at the furnace 670 may provide power to the various componentsof the subnet 615, and a transformer located at the furnace 695 mayprovide power to the various components of the subnet 620 via R and Clines. As illustrated, the C line may be locally grounded.

This approach differs from conventional practice, in which sometimes amaster controller has the ability to see or send commands to multiplecontrollers in a single location, e.g., a house. Instead, in embodimentsof which FIG. 6 is representative there is no master controller. Anycontroller (e.g. UI, or SC) may communicate with any device, includingother controllers, to make changes, read data, etc. Thus, e.g., userlocated on a first floor of a residence zoned by floor may monitor andcontrol the state of a zone conditioning a second floor of the residencewithout having to travel to the control unit located on the secondfloor. This provides a significant convenience to the operator.

FIG. 7A illustrates an example embodiment of a zoned HVAC system,generally denoted 700A. A residence 705 has an HVAC data processing andcommunication network that includes two zones 710, 715. The zone 710includes a bathroom 720 and a bedroom 725. A demand unit 730, e.g., agas or electric furnace, located in a basement 735 provides heated orcooled air to the zone 710 via source vents 737 and return vents 739.The zone 715 includes a laundry room 740, a bathroom 745 and a livingroom 750. A demand unit 755, which again may be a gas or electricfurnace, provides heated or cooled air to the zone 715 via source vents757 and return vents 759.

The zone 710 also includes comfort sensors 760, 765, 770, userinterfaces 775, 780 and a subnet controller 784. The zone 715 includes acomfort sensor 785, a user interface 790, and a subnet controller 792.The subnet controller 792 may be optionally omitted with the subnetcontroller 784 is configured to control both of the zones 710, 715. Thecomfort sensors 760, 765, 770, user interfaces 775, 780 and the demandunit 730 are networked to form a first subnet. The comfort sensor 785,user interface 790 and demand unit 755 are networked to form a secondsubnet. The two subnets are in turn connected to form the network asdescribed with respect to FIG. 6.

In the illustrated embodiment, the user interfaces 775, 780 arephysically associated with the first zone 710, and the user interface790 is physically associated with the second zone 715. Furthermore, thesubnet controller 784 is physically associated with the first zone 710,and the subnet controller 792 is physically associated with the secondzone 715. Herein, a user interface or subnet controller is physicallyassociated with a zone when the subject user interface or subnetcontroller is located in a space that is conditioned by that zone. Thus,e.g., the subnet controller 784 is not physically associated with thesecond zone 715. A subnet controller or user interface may be logicallyassociated with a particular zone, even if the subnet controller or userinterface is not physically associated with that zone. By logicallyassociated, it is meant that the subnet controller or user interface mayoperate in some configurations to control the ambient conditions of thezone with which the subnet controller or user interface is logicallyassociated.

Herein and in the claims, a zone is a portion of a networked HVAC systemthat includes at least one demand unit, at least one user interface andat least one comfort sensor. In some cases, as described below, a singledemand unit may serve more than one zone. A room of a conditionedstructure typically is only conditioned by a single zone. Thus, e.g.,the rooms 720, 725 receive air from one of the vents 737, and the rooms740, 745, 750 receive air from one of the vents 757. A zone may bephysically configured to condition one level of a multi-level structuresuch as the residence 705, but this need not be the case. For example, anetworked HVAC system may be zoned to provide independent conditioningof southern and northern facing portions of a structure to account fordiffering heating and cooling loads.

The comfort sensors 760, 765, 770 may be positioned in any location atwhich a user wishes to locally sense a temperature or RH. In some casesa particular comfort sensor is collocated with a user interface, suchas, e.g. the comfort sensor 770 and user interface 780. A collocatedcomfort sensor and user interface may be logical devices of a singlephysical unit, or may be discrete physical units. For example, it may beconvenient for the comfort sensor 770 and the user interface 780 to belocated in an enclosure 782 to present to the operator a familiar lookand feel associated with conventional thermostats. Optionally, thesubnet controller 784 is also located within the enclosure 782. Asdescribed previously, the comfort sensor 770 and the user interface 780remain independently addressable in the subnet and the network even withhoused in a same enclosure. In other cases a comfort sensor is locatedwithout being collocated with a user interface. One example is thecomfort sensor 765. As described further below, any of the userinterfaces 775, 780, 790 may be collocated with an active subnetcontroller, which may control any demand unit in the HVAC network tomaintain a temperature or RH measured by any of the comfort sensors 760,765, 770, 785.

FIG. 7B illustrates an example embodiment of a zoned HVAC system,generally denoted 700B. In the system 700B, the demand unit 730 providesheating and/or cooling to both zones 710, 715. The system 700B isillustrative of embodiments in which one or more dampers 115, acting aszone controllers, open or close air paths to various portions of thesystem 700B to provide zoned operation. In the illustrated embodiment, azone controller 794 (e.g. a damper) controls air flow to the zone 710,while a zone controller 796 (e.g. another damper) controls air flow tothe zone 715. Each zone controller 794, 796 is controlled by acorresponding zone controller module 215 (not shown). The zonecontrollers 794, 796 are controlled by an active subnet controller,e.g., the subnet controller 784, that is configured to use one or moreof the comfort sensors 760, 765, 770 to control the temperature of thezone 710, and to use the comfort sensor 785 to control the temperatureof the zone 715. In various embodiments, the temperatures of the zones710, 715 are independently controlled by controlling air flow to thezones via the zone controllers 794, 796. In some embodiments, the demandunit 730 is configured to provide greater air flow to one of the zones710, 715 than the other to compensate for greater heating or coolingload or air flow requirements.

The subnet controller 784 may be configured to automatically detect thepresence or register the absence of the demand units 730, 755 and thezone controllers 794, 796. In some embodiments, the subnet controller784 automatically self-configures for zoned operation, e.g.independently controlling the temperature of the zones 710, 715, in theevent that both of the demand units 730, 755 are detected. In anotherembodiment, the subnet controller 784 automatically self-configures forzoned operation in the event that only one of the demand units 730, 755is detected, but both of the zone controllers 794, 796 are detected. Inanother embodiment, the subnet controller 784 automaticallyself-configures for unzoned operation in the event that only one of thedemand units 730, 755 is detected, and neither of the zone controllers794, 796 is detected. In other embodiments, the subnet controller 784 isconfigured for zoned or unzoned operation manually by an installer viathe user interface 780.

In an embodiment, the zones 710, 715 are configured as separate activesubnets. In such embodiments, the subnet controller 784 and the subnetcontroller 792 (FIG. 7A) are both active subnet controllers. Each of thesubnet controllers 784, 792 may discover the presence of the other ofthe subnet controllers 784, 792, and thereby detect the presence of theassociated active subnet, during a system initialization state.Discovery may be made, e.g., via a message sent by one of the subnetcontrollers 784, 792 to the demand units 730, 755 prompting the demandunits 730 755 to respond. The subnet controllers 784, 792 may beconfigured to recognize that each zone 710, 715 meets or exceeds aminimum configuration necessary to support zoned operation andself-configure such that each subnet controller 784, 792 acts as anactive subnet controller within its respective zone 710, 715. In somecases, one or both of the subnet controllers 784, 792 is configured suchthat discovery of both demand units 730, 755 is sufficient to triggerself-configuration for zoned operation.

FIG. 8 illustrates an embodiment of a state sequence generallydesignated 800 that describes a set of states in which the aSC 230 a mayoperate. In a state 810, the aSC 230 a is reset. The state 810 may bereached by a power-up reset or a maintenance command, e.g. The aSC 230 aadvances to an initialization state 820, designated “subnet startup”.Optionally, each local controller 290 may perform a memory functionaltest, e.g., a CRC check, between the reset state 810 and the subnetstartup state 820.

In the subnet startup state 820, the one or more subnet controllers 230may discover which devices are present in the network 200. Discovery maytake the form, e.g., of a series of discovery messages over the data bus180 from the one or more subnet controllers 230, and associated replymessages from the devices present.

Recalling that in various embodiments there may only be a single activesubnet controller in a subnet, the one or more subnet controllers 230arbitrate to determine which assumes the role of the aSC 230 a. Thisarbitration may take place during the subnet startup state 820. If thereis only one subnet controller 230, then the arbitration process istrivial. If there is a plurality of subnet controllers 230, the subnetcontrollers 230 of the plurality may exchange messages over the data bus180 that are configured to allow the subnet controllers 230 to determinethe most suitable subnet controller 230 to act as the aSC 230 a. Thisarbitration may be based on a set of features and parameters of eachsubnet controller and may further be designed to ensure that the “best”subnet controller 230 available controls the subnet. For example, onesubnet controller 230 may be a more recent manufacturing revision thananother subnet controller 230, or may be configured to control a newcomponent of the system 100 that other subnet controllers 230 are notconfigured to control. Is these examples, the subnet controller 230 withthe more recent revision, or that is configured to control the newcomponent would be regarded as the “best” subnet controller 230.

After this arbitration, one subnet controller 230 may become the aSC 230a, and from this point on may perform all control functions related tooperation of the subnet of which it is a part. The aSC 230 a maydetermine that the subnet is in a configuration state or a verificationstate, and may further assign or reassign all operating parameters suchas equipment types and subnet IDs to all members of network 200.Generally, in a configuration state the aSC 230 a may assign all systemparameters to all the members of the network 200. In the verificationstate, the aSC 230 a may verify that the parameters stored by each localcontroller 290 are correct, and restore any values that are determinedto be incorrect.

In the discovery process, the aSC 230 a may determine that a pluralityof demand units 155 is present in the network 200. For example, the aSC230 a may send a message addressed to a demand unit 155, in response towhich the demand unit 155 sends a reply message. In some cases, the aSC230 a may detect the presence of one or more damper controller modules215 and comfort sensors 260. In this event, the aSC 230 a mayautomatically self-configure for zoned operation. Self-configuration mayinclude, e.g., associating a first comfort sensor 260 and a first UI 240with a first zone, and associating a second comfort sensor 260 and asecond UI 240 with a second zone. The zones may, but need not,correspond to different subnets of the network 200. In the event that nodamper controller module 215 is discovered, e.g. a single furnace 120,the aSC 230 a may self-configure for unzoned operation.

After the subnet startup state 820, the network 200 may enter acommissioning state 830. Generally, during the commissioning state 830functional parameters of each local controller 290 may be set toproperly operate within the context of each other local controller 290.For example, a blower unit may be configured during the commissioningstate 830 to provide an air flow rate that is consistent with a heatoutput rate of a heat pump. The network 200 may remain in thecommissioning state 830 until each local controller 290 therein isconfigured.

After the commissioning state 830, the network 200 enters an installertest state 840. In some cases, the network 200 remains in the installertest state 840 only as long as is necessary to determine if installertest functions are requested. If none are requested, the sequence 800may advance immediately to a link state 850. If installer test functionsare requested, e.g. via the UI 240, then the network 200 remains in theinstaller test state 840 until all requested functions are complete andthen advances to the link state 850.

The sequence 800 may enter the link mode, e.g., upon request by aninstaller via the UI 240. For example, during installation, aninstallation routine may provide an option to enter the link state 850to link subnets, e.g., the subnets 615, 620 (FIG. 6). In the link state850, any subnets of the network 200 are configured to operate together.For example, a first subnet ID may be assigned to each local controller290 in the subnet 615, and a different second subnet ID may be assignedto each local controller 290 in the subnet 620.

After the operations necessary to link the subnets, the sequence 800 mayadvance to the normal operating state 860. It is expected that thesystem 100 will be in the normal operating state 860 for the vastmajority of its operation.

FIGS. 9-30 and associated discussion describe various aspects of theoperation of a user interface. In various embodiments, the userinterface includes a display to present information to a user. Invarious embodiments the display is touch-sensitive to allow the user toselect display modes and operational attributes by touching anappropriately configured portion of the display.

Turning first to FIG. 9, illustrated is a user dashboard 900. The userdashboard 900 may be considered a general “palette” upon whichinformation is presented to a user of the user interface. In someembodiments an installer dashboard is used to present information to aninstaller or service provider, the installer dashboard being presentedin an installer mode that is not accessible to the operator in routineoperation. The user dashboard 900 may be implemented using atouch-screen device, e.g. In the illustrated embodiment, eight tabs 910,920, 930, 940, 950, 960, 970, 980 are shown without limitation. Thevarious tabs may be associated with functions or routines associatedwith different operational aspects of the system 100. Each tab mayfurther have a unique screen associated therewith appropriate to thefunctions or routines provided under that tab. A service soft switch 990may provide a means for a service technician to access one or moreservice screens as discussed with respect to FIG. 31 below. Selection ofsoft switches on the service screens may invoke various setup and/orcalibration routines, e.g. Optionally, the switch 990 may also double asa manufacturer logo.

In the illustrated embodiment, selection of the tab 910 accessesweather-related functions. The tab 920 is associated with indoorhumidity display and control. When the tab 930 is selected the userdashboard 900 presents alert data to the user. The tab 940 provides helpinformation.

Along the bottom of the user dashboard 900, the tab 950 is associatedwith indoor settings, e.g., operational attributes of the HVAC systemthat result in a particular temperature and/or RH of the conditionedspace of a residence. For example, pressing the tab 950 may cause thedisplay 905 to present an indoor temperature settings screen asdescribed further below. The tab 960 allows the user to view and modifyoperating programs. The tab 970 allows the user to view and modifyoperating attributes of one or more zones of the HVAC system. The tab980 selects a home screen that may provide a summary of operationalattributes and environmental data.

The user dashboard 900 may be regarded as tailored for used when thesystem 100 is not zoned. For instance, when an HVAC system is zoned,typically a temperature set point is set for each zone. Thus, the tab950, which in the illustrated embodiment is configured to provide accessto “indoor settings”, may be undesirable in a zoned system 100, sinceeach zone may have a temperature setting specific to that zone. Thus, insome cases, discussed below with respect to FIG. 22B, the tabs 950, 960may be replaced with tabs appropriate to zoned applications.

The screens associated with each tab 910, 920, 930, 940, 950, 960, 970,980 may be accessed by touching the desired tab. Thus, in oneembodiment, touching the tab 910 presents a screen associated withweather-related functions. Each screen associated with a particular tabmay be accessed by touching that tab. In addition, in some cases ascreen associated with one tab may be accessed directly from a screenassociated with a different tab. Thus, for example, a screen associatedwith the indoor settings tab 950 may include a link, in the form of asoft switch, to a screen associated with the “indoor humidity” tab 920.This aspect is expanded upon below.

FIG. 10 illustrates an example embodiment of access transitions betweenthe various screens associated with each tab 910, 920, 930, 940, 950,960, 970, 980. A weather screen 1010 is associated with the weather tab910. An indoor humidity screen 1020 is associated with the indoorhumidity tab 920. An alert screen 1030 is associated with the alerts tab930. A help screen 1040 is associated with the help tab 940. An indoorsettings screen 1050 is associated with the indoor settings tab 950. Aprograms screen 1060 is associated with the programs tab 960. A zonessummary screen 1070 is associated with the zones tab 970. A home screen1080 is associated with the home tab 980.

A path 1082 connecting each of the screens 1010, 1020, 1030, 1040, 1050,1060, 1070, 1080 reflects the ability of the used to access each screenby touching the tab associated with that screen, regardless of thepresent state of the display 905. In some embodiments, each of thescreens 1010, 1020, 1030, 1040, 1050, 1060, 1070, 1080 times out after aperiod of inactivity, e.g. about 5 seconds. Paths 1084, 1086 mayrepresent the screen transition that results upon timeout. In someembodiments the home screen 1080 includes a soft switch that activatesthe indoor settings screen 1050 to allow the user to easily navigate tofunctionality thereof via a path 1088. In some embodiments the homescreen 1080 also includes an active alert annunciator that when selectedcauses the alert screen 1030 to be displayed via a path 1089. Finally,in some embodiments an alert may be displayed via a pop-up alert window1090. The pop-up alert window 1090 may be displayed from any otherscreen, and so is illustrated as being independent of the paths 1082,1084, 1086, 1088 and 1089.

Turning to FIG. 11, an embodiment, generally designated 1100, of thehome screen 1080 is illustrated without limitation. The features of thehome screen 1080, described following, are examples of features thatsome residential users of the system 100 may find useful. Those ofordinary skill in the pertinent arts will appreciate that otherfeatures, and graphical layout of features, are within the scope of thedisclosure.

The home screen 1080 includes two panels 1105, 1110. The panel 1105presents a current status of indoor conditions, while the panel 1110presents weather information. The panel 1105 includes a display ofcurrent temperature, as determined by a comfort sensor 160 e.g., and atemperature set point. The temperature set point may be selected by softswitches 1115, 1120. A humidity status message 1125 indicates whetherindoor humidity, which again may be determined by a comfort sensor 160,is within selected limit. A program status message 1130 indicateswhether the UI 240 is running a heating/cooling program, as describedfurther below. Finally, a “press for more” soft switch 1135 provides ameans to enter a display mode that provides additional information andconfiguration choices to the user.

The panel 1110 includes an indication of outside air temperature, asdetermined, e.g., by an optional outdoor sensor. Outside humidity may bedisplayed, also as determined by an outdoor sensor. A condensed weatherforecast may also be provided, including, e.g., anticipated high and lowtemperature and a sky condition graphic 1140. A “press for more” softswitch 1145 provides a means to enter a display mode to obtainadditional weather-related information. The weather information may bereceived by the aSC 230 a via the UI/G 250, e.g., or may be inferredfrom barometric pressure trends.

FIG. 12 illustrates an example embodiment, generally designated 1200, ofthe indoor humidity screen 1020 that may be displayed in response toselecting the humidity status message 1025, or selecting the humiditytab 920. In the illustrated embodiment, the indoor humidity screen 1020includes subpanels 1205, 1210, 1215. The subpanel 1205 displays currentindoor humidity 1220, humidity set point 1225, and a graphic 1230representing a range of humidity values. Advantageously, in someembodiments, the graphic 1230 is predetermined, e.g., via firmware, tospan a range of humidity that is expected to be comfortable to occupantsof the structure conditioned by the system 100. Soft switches 1235, 1240provide a means to respectively increase or increase the humidity setpoint.

The subpanel 1210 presents a summary view of settings of the system 100relevant to humidity control. In various embodiments the system 100 maybe configured to provide humidification, dehumidification or both. Inthe example embodiment of the subpanel 1210, humidify/dehumidify ischecked, indicating to the user that the system 100 is enabled toincrease or decrease moisture in the air to control for the humidity setpoint. In other embodiments, only dehumidification or onlyhumidification is enabled, such as to reduce energy consumption, orbecause needed equipment is not installed to provide the unselectedfunction, e.g. In some embodiments, “off” is checked, such as when nohumidification/dehumidification capability is present in the system 100.A soft switch 1245 provides a means to switch between the variousconfiguration options shown in the subpanel 1210.

The subpanel 1215 provides a status message indicating whether theindoor humidity screen 1020 is configured to display humidificationsettings or dehumidification settings. A soft switch 1250 provides ameans to switch between humidification status and dehumidificationstatus.

FIG. 13 illustrates an example embodiment, generally designated 1300, ofthe alert screen 1030 of the disclosure. In the illustrated embodiment,the alert screen 1030 includes an alert field 1310 and soft switches1320, 1330, 1340, 1350, 1360. The alert field 1310 may be used todisplay information relevant to a system status of condition, such as amaintenance item, component failure, etc. A maintenance item may bereplacement of a consumable part, such as a filter, humidifier pad, orUV lamp. The set of functions provided by the soft switches 1320, 1330,1340, 1350, 1360 may be tailored to provide the operator with convenientaccess to various alert-related utilities.

An embodiment is presented without limitation to the types of utilitiesprovided thereby. More specifically, the soft switch 1320 providesservice information. The soft switch 1330 provides a reminder function.The soft switch 1340 provides a means to edit alert reminders. The softswitch 1350 clears an alert or alarm, and the soft switch 1360 selectsthe next alert/alarm when multiple alerts or alarms are activesimultaneously.

FIG. 14A illustrates one embodiment generally designated 1400A ofmanaging alerts/alarms in the system 100. Those skilled in the pertinentart will appreciate that the UI 240 may be configured to provide otherfunctionality that that illustrated by FIG. 14A within the scope of thedisclosure. Referring first to the service soft switch 1320, selectionthereof may cause a service screen 1410 to be displayed. The servicescreen 1410 may present service-related information to the user, suchas, e.g., local service provider contact information, a manufacturer ordealer help line, etc. Pressing a “back” switch returns the display tothe alert screen 1030.

In some embodiments the reminder soft switch 1330 is inactive (e.g.,“grayed out”) for high-priority alarms or alerts, such as for a failedfan motor. For those cases in which the switch 1330 is active, thedisplay 905 transitions to a screen 1420 when the user selects theswitch 1330. The screen 1420 may present more detailed information aboutthe alert. For example, a description of a replacement consumable may bepresented, or information on the advisability of delaying action. Theuser may press a “cancel” switch to return the display 905 to the alertscreen 1030.

Alternatively, the user may press a “set” switch, which cases a screen1430 to be displayed. The screen 1430 may display the same or differentinformation regarding the alert, and may present an adjustable timefield and soft switches to allow the user to select a future time or adelay time before being reminded again of the alert/alarm. In anembodiment, the reminder delay time may be set to one of 1 day, 1 week,1 month and three months. In another embodiment, the reminder delay timemay be set to a custom time delay of any duration. The alert will thenbe generated again after the expiration of the time delay. The user mayselect a “cancel” switch to return to the alert screen 1030 withoutsaving changes, or a “set” switch to advance to a screen 1440. Thescreen 1440 may present to the user a summary of the requested delaytime for confirmation. The user may press a “done” switch to return thedisplay 905 to the alert screen 1030.

In some cases, the alert/alarm is cleared, e.g., after replacing aconsumable. The user may select the clear soft switch 1350 to reset thealert/alarm. The alert/alarm may be generated again at a future dateafter the expiration of a time period associated with that alert/alarm.For example, a filter may be routinely replaced every three months. TheUI 240, the SC 230 or a demand unit using the filter may be configuredto generate the alert/alarm after the expiration of three months.

Thus, when the user selects the clear soft switch 1350, the display 905advances to a screen 1450. The screen 1450 presents a confirmationmessage to confirm that a service activity related to the alert/alarmhas been performed. If the user selects a “no” switch, the display 905returns to the alert screen 1030. If the user selects a “yes” switch,the display advances to a screen 1460. The screen 1460 may presentinformation associated with the alert/alarm, and a “set” switch and“cancel” switch. If the user selects the cancel switch, the display 905returns to the alert screen 1030. If the user selects the set switch,then, the display 905 may advance to one of two screens in theillustrated embodiment.

The display 905 advances to a screen 1470 in the case that thealert/alarm has a custom service period associated therewith. In thiscase, the screen 1470 may again present service information, and alsopresents a time field and selection switches. The user may select thedesired service time, and select a “set” switch. Alternatively, the usermay select a “cancel” switch, which returns the display 905 to the alertscreen 1030. For the case that the user selects the “set” switch, thedisplay 905 advances to a confirmation screen 1480. The screen 1480presents a confirmation message and a “done” switch. The display 905returns to the alert screen 1030 when the user selects the “done”switch.

For the case that an alert/alarm does not have a custom time associatetherewith, the alert/alarm may have a default time associated therewith.In this case, when the user selects the “set” switch on the screen 1460,the display 905 advances directly to the screen 1480 for confirmation.

Referring again to the alert screen 1030, the edit soft switch 1340provides a means for the operator to edit a reminder already stored inaSC 230 a memory. Selecting the switch 1340 may display a screen listingactive reminders available for editing. Selection of a reminder from thelist may then cause the display 905 to advance to the screen 1430,wherein the operator may enter desired delay time.

FIG. 14B illustrates another embodiment of a method generally designated1400B of managing alerts/alarms in the system 100. The method 1400Bgenerally pertains to alerts/alarms that are displayed on the display905 by a pop-up window. Thus, the method 1400B begins with a state 1485that may be entered from any active screen of the display 905. From thestate 1485, the method 1400B displays a screen 1490 that presentsinformation regarding the alert/alarm to the operator. The screen 1490,an alternate embodiment of the alert screen 1030, includes a “remindlater” switch, a “clear” switch and a “done” switch. When the operatorselects the “remind later” switch, the method advances to the screen1420, and continues as described previously. When the operator selectsthe “clear” switch, the method advances to the screen 1450, andcontinues as described previously. When the user selects the “done”switch, the method 1400B returns to the state 1485, e.g., the screenthat was active before the screen 1490 was displayed.

Turning now to FIG. 15, a help screen generally designated 1500 isillustrated. The help screen 1500 may be displayed by the display 905when the operator selects the help tab 940. In the illustratedembodiment, the help screen 1500 displays a help field 1510, a cleandisplay field 1520, a user settings field 1530, and a dealer informationfield 1540. The behavior of the fields 1510, 1520, 1530 are described inthe context of FIG. 16, below. The field 1540, when selected, maypresent to the operator information regarding the dealer, manufactureror installer, such as contact information, address, etc.

FIG. 16 illustrates an embodiment of a method generally designated 1600of providing help to the operator via the display 905. Addressing firstthe help field 1510, selection thereof causes the display 905 to advanceto a screen 1610. The screen 1610 displays textual information to theoperator in a text field 1615. In some embodiments, the text field 1615is also configured to be touch-sensitive, so that the display text maybe advanced to a previous or a prior page, e.g., or so the display 905reverts to a screen that was displayed prior to selection of the helpfield 1510.

Selection of the clean display field 1520 causes the display 905 toadvance to a screen 1620. The screen 1620 is configured to allow thedisplay 905 to be cleaned. Thus, e.g., a suitable message may bedisplayed, and all touch-sensitive regions of the display 905 may bedisabled so that no inadvertent action is selected by contact duringcleaning. The display 905 may be further configured to automaticallyreturn to the screen 1040 after a limited period, e.g., about 30seconds, thus terminating the cleaning period.

When the user settings field 1530 is selected, the display 905 advancesto a screen 1630. The screen 1630 provides an initial screen forselection of a family of parameters to modify. In one embodiment, thescreen 1630 presents a field 1635 that displays a list of subnetcontroller variables, a list of local UI settings, and a list ofreminders. In some embodiments, each list is sequentially presented tothe user by a brief touch or tap of the field 1635. In anotherembodiment, the various list items are accessed by scrolling through alist of items. The user may select a list item by tapping thereon andselecting a “modify” switch. The action taken by the display 905 may becontext sensitive, e.g., may depend on the type of parameter selected.For example, in the illustrated embodiment, selecting a subnetcontroller or a UI parameter causes the display 905 to advance to ascreen 1640 when the modify switch is selected. Alternatively, selectinga reminder item causes the display 905 to advance to a screen 1650 whenthe modify switch is selected.

When the screen 1640 is active, the display 905 may present amodification field 1645. The field 1645 may be configured to provide,e.g., up/down arrows or alpha-numeric keypad to allow the operator tomodify the selected parameter. After modifying the parameter value, theuser may select a “save” switch to store the modified parameter valueand return to the screen 1630. Alternatively, the user may select a“cancel” switch that causes the display 905 to return to the screen 1630without modifying the selected parameter.

As described, in the event that the user selects a reminder formodification, the screen 1630 may advance to the screen 1650. The screen1650 is illustrated having a “reminder current setting” field 1653 and a“reminder options” field 1656. The field 1653 may present the currentsettings associated with the selected reminder. The field 1656 mayinclude up/down switches or a keypad to allow the operator to modify thereminder settings or options. The operator may select a “set” switch tosave the modifications, or a “back” switch to return to the screen 1630without saving changes. The action resulting from selecting the “set”switch may depend on the type of reminder, e.g., a reminder that allowsa custom reminder time or a reminder that does not. If the reminderallows a custom reminder time to be associated therewith, selecting the“set” switch causes the display 905 to advance to a screen 1660. If thereminder has a fixed reminder time associated therewith, the display 905advances to a screen 1670.

Within the screen 1660, a “reminder current setting” field 1663 and a“custom date & time” field 1666 are presented. The field 1663 maypresent the current value of the reminder time. The field 1666 mayinclude up/down switches or a keypad to make changes. The operator mayselect a “cancel” switch to exit the screen 1660 without saving changesto the selected reminder, or may select a “set” switch to advance to thescreen 1670. Within the screen 1670, the display 905 may present aconfirmation of the selected reminder and reminder time. The operatormay then select a “done” switch, thereby causing the display 905 toreturn to the screen 1630.

Turning now to FIG. 17, illustrated is an embodiment of the indoorsettings screen 1050. The indoor settings screen 1050 includes atemperature conditions and settings field 1710. The field 1710 mayinclude, e.g., current indoor temperature and temperature set points. Insome embodiments the temperature set points may be selected by up/downswitches 1715, 1720. A system settings field 1730 indicates whether thesystem 100 is configured to heat, cool or heat and cool, or is off. Aselect switch 1731 may be used to change the system setting. A fansettings field 1740 indicates whether the fan associated with an airhandler 110, e.g. is configured to operate automatically, is constantlyon, or is set to circulate air. In this context, the system 100circulates air by ensuring the fan operates with a minimum duty cycle,independent of heating and cooling requirements, so ensure a desiredturnover rate of the air in the zone. Such operation may beadvantageous, e.g., for air filtering. A select switch 1741 may be usedto change the fan setting. In some cases, the indoor settings screen1050 pertains to a selected zone.

FIG. 18 illustrates an embodiment in which the UI 240 is running aprogram schedule. In some embodiments, selecting either of the switches1715, 1720 causes the indoor settings screen 1050 to advance to a screen1810. The screen 1810 provides a “hold options” field 1812. Selection ofa “cancel” switch therein returns the display 905 to the indoor settingsscreen 1050. On the other hand, selection of a “standard” switchadvances to a screen 1820. Within the screen 1820, the user may select apre-programmed hold period from one or more options.

Without limitation, preprogrammed hold periods may be 1 hour, 2 hours, 8hours, or 24 hours. In some embodiments, the screen 1820 may provide theoperator the option of holding the temperature and/or system and/or fanset points until a next scheduled period of the running programschedule. If the operator selects a “set” switch the UI 240 saves thehold options and returns to the indoor settings screen 1050.Alternatively, the operator may select a “cancel” switch to return tothe indoor settings screen 1050 without saving any hold options.

Returning to the screen 1810, if the operator selects a “custom” switchin the field 1812, the display 905 advances to a screen 1830. Within thescreen 1830, the user may select a “cancel” switch to return to thescreen 1810. If the user selects a “set” switch, the display 905advances to a screen 1840 on the first invocation of the set switch.Within the screen 1840, the operator may select a custom hold time. Inone example, the hold time limited to a time at least 15 minutes in thefuture. The operator may then select a “back” switch to return to thescreen 1830. Upon selecting the “set” switch on the screen 1830 for asecond time, the display 905 advances to the screen 1820, which operatesas previously described.

FIG. 19 illustrates an example embodiment of a program screen 1910configured to program a temperature schedule. The programs screen 1910may be displayed, e.g., by selecting the programs tab 960 (FIG. 9). Theprograms screen 1910 includes four program columns. Each column has anassociated time at which a program period begins. Each column allows theoperator to select a heat temperature, a cool temperature, and a fanmode. Note that in the fourth column, with a corresponding time of 10:30PM, the heat temperature, cool temperature, and fan mode are missing,indicating that this program period is not being used in the currentprogram. Note also that in the illustrated embodiment the tabs 910, 920,930, 950, 960, 970 are absent. The operator is thus restricted toselecting the help tab 940 or the home tab 980. Those skilled in thepertinent art will appreciate that other choices of screen configurationare within the scope of the disclosure. Of course, selecting otherswitches, e.g. a “save”, “cancel” or “back” switch may cause anotherscreen to be displayed. Those skilled in the pertinent art willappreciate that other choices of screen configuration are within thescope of the disclosure.

The UI 240 may be preprogrammed by the manufacturer with a temperatureprogram. In one illustrative embodiment, the UI 240 is preprogrammedwith an Energy Star compliant schedule. The following table illustratesone such schedule:

PERIOD TIME HEAT COOL FAN 1  6 AM 70 78 Auto 2  8 AM 62 85 Auto 3  5 PM70 78 Auto 4 10 PM 62 82 AutoThe Energy Star schedule may be a “default” schedule that the operatormay modify or restore in various circumstances as described furtherbelow.

FIG. 20 illustrates an embodiment of a method 2000 of operating the UI240 to program an operating schedule. The method 2000 begins with anevent 2010 corresponding to selection of the programs tab 960 by theoperator. The display 905 then presents a screen 2020 that prompts theoperator to select whether to enable operation of a stored program. Ifthe operator chooses to disable program operation or to maintaindisabled program operation if program operation was already disabled,the operator may end the dialog by selecting the home tab 980.Alternatively, if the operator wishes to operate the system 100 using aprogram schedule, the operator may select a “view/edit” switch or a“restore” switch.

As the UI 240 is configured in the method 2000, selection of the“restore” switch of the screen 2020 restores the operating program to apreprogrammed operating program, e.g., the Energy Star default programexemplified by the table above. If the operator elects to restore theprogram by selecting the “restore” switch of the screen 2020, then thedisplay advances to a confirmation screen 2030. Selection of a cancelswitch therein causes the display 905 to return to the screen 2020without saving changes. Alternatively, selection of a “confirm” switchcauses the display 905 to advance to a summary screen 2040.

The screen 2040 presents a program schedule group that includes a daysummary field and a schedule summary field. These fields are configuredin the illustrated embodiment to cause the display 905 to advance toanother screen when selected. These fields may also include a summary ofthe associated program entity. Thus, e.g., the day summary field maypresent a summary of the day or days associated with a program group,and the schedule summary field may present a summary of the time and setpoints associated with the program group.

When the operator selects the day summary field, the display 905advances to a screen 2050. Alternatively the screen 2050 may bedisplayed if the operator selects a “new” switch in the screen 2040. Inthe illustrated embodiment the screen 2050 includes a “7 day” field, a“mon-fri” field and a “sat-sun” field. Selection of one of these fieldsselects the days of the week associated with that switch. Alternatively,the operator may select a “day selection” field that allows the operatorto select any combination of days that are not otherwise scheduled. Theoperator may select a “cancel” switch to discard changes and return tothe screen 2040, or may select a “next” field to advance to a screen2060.

The screen 2060 includes a “schedule settings” field and up/down arrows.The user may select a value within the schedule settings field, e.g.,time or set points, and change the selected parameter to a desired valueusing the up/down arrows. The user may select a “cancel” switch todiscard changes and return to the screen 2040, or may select a “back”switch to return to the screen 2050. From this screen, the operator mayselect another unscheduled day or days and select parameters associatedwith these days via the screen 2060. The operator may select a “save”switch in the screen 2060 to save all changes to the schedule and returnto the screen 2040.

Turning now to FIG. 21, illustrated is an embodiment of the zonessummary screen 1070. The zones summary screen 1070 displays one or morezone summary fields, e.g. fields 2110 a-f, one summary field 2110 a-fbeing associated with each zone of the system 100. Each summary field2110 a-f includes the zone name and the current temperature of thatzone. The zone name may be named more specifically, e.g., kitchen,upstairs, etc. While six zones are shown in the illustrated embodiment,in some cases the system 100 includes more that six zones, or includesmore zones than will fit on a single screen of the display 905. In sucha case, the zones summary screen 1070 may include a “next” switch and a“previous” switch to navigate among as many screens as are necessary topresent all the zones.

FIG. 22A illustrates an embodiment generally designated 2200 ofoperation of the display 905 when the zones tab 970 is selected. Fromthe zones summary screen 1070, the display 905 may advance to a zonesetting screen 2210 when, e.g., one of the zone summary fields 2110 a-fis selected.

Turning momentarily to FIG. 22B, illustrated is one embodiment of thezone setting screen 2210 for a particular zone, e.g. a “kitchen zone”.The screen 2210 includes a setpoint field 2212, a system settings field2214 and a fan settings field 2216. The fields 2212, 2214, 2216 displayinformation about and allow changes to only parameters associated withan indicated zone, e.g. “kitchen”. The setpoint field 2212 may befunctionally similar to the indoor settings screen 1050 (see, e.g.,FIGS. 17 and 18), and may include, e.g., a temperature/set point display2218, and up/down switches 2220 to adjust the temperature set point. Thescreen 2210 also includes a back switch 2222 that when selected mayreturn the display 905 to the zones summary screen 1070. A programswitch 2224 may be used to activate a program screen, e.g. similar tothe programs screen 1910, associated with the indicated zone. In theillustrated embodiment, the screen 2210 includes a whole-house overridetab 2227 and a whole house program tab 2229 the operation of which isdiscussed below.

The operation of the screen 2210 may be similar to that of the indoorsettings screen 1050, but may be configured to control only aspects ofthe selected zone. The operator may make any desired changes and thenselect the zones tab 970 to return to the zones summary screen 1070 ifdesired to make changes to other zones. Alternatively, the operator mayselect any of the other tabs 910, 920, 930, 940, 950, 960, 980 to exitthe screen 2210.

Returning to FIG. 22A, when the operator selects the program switch2224, the display 905 may advance to a program summary screen 2226. Thesummary screen 2226 may include a schedule summary field 2228 that maypresent to the operator a summary of a step programmed for the zoneselected via one of the zone summary fields 2110 a-f. A program switch2230 may be configured to select a program operation mode for theselected zone. For example, successive selection of the switch 2230 maycycle the program operation for the selected zone between off,independent program operation, and operation in which the selected zonefollows a house-level program. When independent program operation isselected, a “new” switch 2232 may become active, allowing the operatorto add a step to the program for the selected zone. If there aremultiple program events for the selected zone, a “next” switch 2234 mayalso be active, allowing the operator to cycle through the existingprogram events.

Returning to the screen 2210, if the operator selects any of thesetpoint field 2212, the system settings field 2214 or the fan settingsfield 2216, the display 905 may advance to a hold options screen 2236.The screen 2236 may again present the user the setpoint field 2212, andfurther provide a set switch 2238 and a clear switch 2240. Selection ofthe clear switch 2240 may return the display 905 to the screen 2210.

Selection of the set switch 2238 may cause the display 905 to advance toa hold settings screen 2242. The screen 2242 may again present the userwith the setpoint field 2212, and further provide a set switch 2244 anda clear switch 2246. Selection of the clear switch 2246 may return thedisplay 905 to the screen 2236. Selection of the set switch 2244 maysave a temperature set point selected via the up/down switches 2220 andreturn the display 905 to the screen 2210.

As noted above, the screen 2210 includes a “whole house override” tab2227 and a “whole house program” tab 2229. These tabs may be used as analternative to the tabs 950, 960, or may temporarily replace the tabs950, 960 only after the user selects the zones tab 970. In this sense,the screen 2210 is tailored for use when the system 100 is zoned. Insome cases, the tabs 2227, 2229 may revert to the tabs 950, 960 afterthe operator exits a screen sequence associated with the zones tab 970.

The whole house override tab 2227 may allow the operator to view, edit,or enable an override function for all zones in the house. In someembodiments the override is effective regardless of the program schedulea particular the zone is running. The whole house override tab 2227 mayalso provide a means for the operator to override a current programschedule in each zone.

The whole house program tab 2229 may allow the operator to view, edit,or enable current program schedule events, and to create additionalprogram schedule events associated with the whole house programschedule. The house program tab 2229 also may be configured to provide ameans to program event times, temperature set points, and the fan modefor each period of the day.

Turning to FIG. 23, illustrated is an embodiment of a whole houseoverride screen 2300 that may be displayed when the whole house overridetab 2227 is selected. The override screen embodiment 2300 includes awhole house temperature field 2310 with which the operator may view atemperature setting and make adjustments to the temperature via up/downswitches 2312. A system settings field 2320 may be used to view andselect a system operation mode, e.g., heat & cool, heat only, cool onlyand off. A fan settings field 2330 may be used to view and select a fanoperating mode, e.g., auto, fan and circulate. A hold options field 2340may be used to view and select a hold time. The hold options field 2340includes, e.g., an adjustable hold time and date, a set switch and aclear switch. Time and date values may be adjusted by adjustmentswitches 2342.

Advantageously, the override screen 2300 provides a means to overrideprogram schedules until the hold time and date for all zones in thesystem 100 from a single display screen, e.g., a single UI 240. The UI240 may communicate the requested hold settings to each subnetcontroller corresponding to each zone in the network 200. Each subnetcontroller may then control the operation of its corresponding zones to,e.g., hold a temperature until the specified end time.

FIG. 24 illustrates operation of the override screen 2300 for overridingzone settings in the system 100. The override screen 2300 may beaccessed by selecting the whole house override tab 2227. If the operatorselects a clear (“C”) switch, the display 905 may return to the homescreen 1080 and discard any changes the operator may have made. If theoperator selects a set (“S”) switch of the screen 2300, the display 905may advance to a screen 2410 in which adjustment arrows may becomeactive to select a custom time & date hold time. Selecting a clearswitch of the screen 2410 may discard any changes and return the display905 to the screen 2300. Alternatively, selecting a set switch of thescreen 2410 may return the display 905 to the home screen 1080. In thecase that the operator does not select the custom hold time option inthe screen 2300, selecting the set switch thereof also may return thedisplay 905 to the home screen 1080.

FIG. 25 illustrates a method generally designated 2500 of settingparameters of a whole house program for the system 100. A whole houseprogram screen 2510 may be displayed when the whole house program tab2229 (FIG. 22B) is selected. The whole house program may override anyzone settings previously set. The screen 2510 may present a schedulesummary field, and “new”, “back” and “next” switches. Selecting theschedule summary field or the “new” switch may cause the display 905 toadvance to a day selection screen 2520. The screen 2520 may include a“day selection” field and a “schedule summary” field, e.g. If a wholehouse program entry already exists, the day selection field may displaythe day of that entry. The schedule summary field may display the timesand set points associated with the displayed day. If a whole houseprogram does not already exist, or in the event the operator selectedthe “new” switch of the screen 2510, the “day selection” field may beselected to choose a day for a schedule entry. The operator may thenselect the “schedule summary” field to advance to a program settingscreen 2530.

The screen 2530 may include a “schedule settings” field. The schedulesettings field may include time and temperature set point subfields. Theoperator may select a desired subfield and use up/down switches toselect a desired value of the selected parameter. Selecting a “cancel”switch in the screen 2520 or the screen 2530 may discard any entries andreturn the display 905 to the screen 2510. Selecting a “save” switch inthe screens 2520, 2530 may return the display 905 to the screen 2510while saving the entries. A “back” switch on the screen 2530 may causethe display 905 to return to the screen 2520, e.g. to select a differentday before saving. In cases in which there are multiple entries in thewhole house program, the “back” and “next” switches of the screen 2510may be active, allowing the operator to select an existing scheduleentry in the whole house program for modification.

FIG. 26 illustrates a method generally designated 2600 of configuringthe system 100. The method 2600 may be advantageously implemented with amicrocontroller or finite state machine, e.g. A method of manufacturingthe UI 240 may include configuring the UI 240 to implement the method2600. In some embodiments, as exemplified by the method 2600, the UI 240is configured to automatically configure the operation of the system 100for zoned operation. The method 2600 begins with an entry state 2610,which may be entered from any appropriate operating state of the system100. In one embodiment, the entry state 2610 is entered during aninitialization phase of the system 100, e.g. the link state 850.

In a state 2620 the UI 240 may discover the presence of a number ofinstances of the comfort sensor 260 in the network 200. Discovery may bemade, e.g., by exchange of messages between the UI 240 and a number ofcomfort sensors 260 over the data bus 180. In a decisional state 2630,the method 2600 advances to a state 2640 in the event that the UI 240discovers only a single comfort sensor 260. In the state 2640 the UI 240self-configures for unzoned operation. Self-configuration may include,e.g., setting various operating parameters associated with zonedoperation to values consistent with operating a single zone, includingvarious display options for the display 905. The method 2600 ends with astate 2695 from which the UI 240 may return to a calling routine.

If more than one comfort sensor is discovered in the state 2620, themethod 2600 branches from the state 2630 to a state 2650 in which the UI240 discovers a number of subnets in the network 200. As described withrespect to FIG. 5, a minimum subnet may include one instance of each ofthe UI 240 and the comfort sensor 160, and a demand unit 155, eachnetworked via a four-wire RSBus. The method 2600 advances to a state2660 in which the aSC 230 a may discover a number of damper controllermodules 215 in the network 200. In a decisional state 2670, the method2600 advances to a decisional state 2680 in the event that the UI 240does not discover additional subnets. In the state 2680, in the eventthat no instances of the damper controller module 215 are discovered themethod 2600 advances to the state 2640 to self-configure for unzonedoperation as previously described.

In the event more than one subnet is discovered in the state 2650, ormore than one damper controller is discovered in the state 2660, themethod 2600 branches from the state 2670 or the state 2680,respectively, to a state 2690. In the state 2690 the UI 240self-configures for zoned operation. Self-configuration may include,e.g., configuring the UI 240 to display a screen tailored for use withan unzoned system in the event that the subnet controller discovers onlycomfort sensor. Self configuration may also include configuring the UI240 to display a screen tailored for use in a zoned system in the eventthat the subnet controller discovers more than one comfort sensor 260and either of more than one subnet or a damper controller module 215.Any additional discovery needed to configure the system 100 may also beperformed in the state 2690.

Configuration for zoned or unzoned operation may include, e.g., openingor closing dampers, communicating with other user interfaces to assignactive and inactive subnet controllers, and setting fan operatingparameters to account for air circulation requirements. When configuringfor zoned operation, the UI 240 may also set various internal parametersto enable presentation of zone configuration screens via the display905. Alternatively, when configuring for unzoned operation, the UI 240may set internal parameters to disable various screens associated withzoned operation so these screens are not presented to an operator.

FIG. 27 illustrates a method generally designated 2700 of operating auser interface. The method is described in a nonlimiting example withreference to FIG. 7A. A method of manufacturing a user interface mayinclude configuring a user interface to implement the method 2700. Themethod 2700 begins with a step 2710 that may be entered from anyappropriate operational state of the system 100.

In a step 2720, the subnet controller 784 operates the zone 710 of thesystem 700A. The subnet controller 784 operates the zone 710 with afirst program schedule. In a step 2730, the subnet controller 792operates the zone 715 with a second program schedule. In a step 2740,one of the user interfaces 775, 780, 790 communicates a hold settingmessage to the subnet controller 784. The subnet controller 792overrides the first and second schedules to operate the zone 710 and thezone 715 according to the hold settings communicated by the holdsettings message. The method 2700 ends with a terminating step 2750.

In general the hold setting message may include, e.g., a temperatureand/or a humidity, a hold start time, a hold stop time, or a holdduration. In a relatively simple embodiment, the message instructs thesubnet controller 784 to maintain a temperature the subnet controller792 is currently configured to maintain until the hold is released by alater message. In a more complex embodiment, the message includes starttime, an end time and a temperature that may be different form thecurrent temperature. In some embodiments, the hold settings arewhole-house settings.

Conventional HVAC zoning uses a single thermostat in each zone, and thethermostats are typically located apart from each other so eachthermostat can monitor the temperature in the zone it controls. Thus,when an operator wishes to set a hold temperature for multiple zones,the operator typically has to set the hold at each thermostat of thesystem for a whole house override.

In contrast, embodiments herein provide the ability for the operator tooverride the program schedules of all zones from a single location,e.g., the user interface 775. The particular user interface 775, 780,790 need not be collocated with any comfort sensor. Thus, holdconditions may advantageously be set form any location in the HVACnetwork at which a user interface is located. The overriding may be donevia the override screen 2300, e.g. In some embodiments, the subnetcontroller 784 communicates hold settings to each user interface 775,780, 790 for display.

FIG. 28 illustrates a method generally designated 2800 of manufacturingan HVAC data processing and communication network. The method isdescribed in a nonlimiting example with reference to FIG. 6, and morespecifically to the UIs 664, 684. The method 2800 begins with an entrystate 2810, which may be entered from any appropriate operating state ofthe system 100.

In a step 2820, the UI 664 is configured to control the operation of thedemand furnace 670. The furnace 670 is associated with the zone 605 byvirtue of being configured to operate in the subnet 615. In a step 2830,the UI 684 is configured to control the operation of the furnace 695.The furnace 695 is associated with the zone 610 by virtue of beingconfigured to operate in the subnet 620. In a step 2840 the UI 664 isfurther configured to override the operation of the UI 684, which areassociated with a different zone, to control the operation of thefurnace 695. The method 2800 ends with a step 2850, from which theoperation of the system 100 may continue in any desired manner.

In some embodiments of the system 100, more than one UI 240 may bepresent on a single system 100, or on a single zone of the system 100.In some embodiments, the operator may thus place multiple UIs 240 on asingle system or zone so the operator can make changes to systemoperating parameters from any of the locations at which the UIs 240 areplaced. In some embodiments, a first UI 240 on a subnet or zone,associated with an active subnet controller, directly controls theoperation of the system or zone. A second UI 240 associated with aninactive subnet controller, on the same subnet or zone may communicatewith the first UI 240, or directly with the aSC 230 a to change systemoperating parameters.

In some embodiments, the first UI 240 is configured to allow an operatorto switch which comfort sensor 160 is given priority by the aSC 230 a.Thus, for example, an aSC 230 a may be associated with any comfortsensor 160 in the subnet, or even in a different subnet. The comfortsensor 160 associated with the aSC 230 a may be collocated in a sameenclosure, such as for the control unit 590, or may be located remotelyfrom the aSC 230 a, e.g., in another room. This capability provides asimple means for the operator to select a particular comfort sensor 260that is in a room occupied by the operator to control the system 100 tomaintain the temperature of the occupied room. In some embodiments, nozoning of the system 100 is needed to provide localized control oftemperature in one or more locations each monitored by a comfort sensor260. In another embodiment, the operator may select an operating mode inwhich the aSC 230 a reads a local temperature of several comfort sensors260 in different locations to determine an average temperature, and thencontrol the system 100 to maintain the desired temperature within aselected range. The several comfort sensors may optionally be collocatedwith user interfaces, and may optionally be collocated with UIs 240.

Accordingly, FIG. 29 illustrates a method generally designated 2900 ofoperating a subnet controller. A method of manufacturing an HVAC dataprocessing and communication network may include configuring variouscomponents of the system 100 to implement the method 2900. The method2900 begins with a step 2910 that may be entered from any appropriateoperational state of the system 100.

In a step 2920, an aSC 230 a controls the demand unit 155 to maintain atemperature at a first location served by a first comfort sensor 160 inresponse to a temperature reported by the first comfort sensor 160. Byway of example, the demand unit may be the furnace 120. The aSC 230 a atthis point does not consider the temperature reported by a secondcomfort sensor 160. The first comfort sensor 160 may be collocated withthe aSC 230 a or located remotely therefrom. In some cases, the firstcomfort sensor 160 is located in a same enclosure with the aSC 230 a,but need not be. In a step 2930, the aSC 230 a controls the demand unit155 to maintain a temperature at a second location served by the secondcomfort sensor 160 in response to the temperature reported by the secondcomfort sensor 160. The aSC 230 a may be configured to control for thesecond aSC 230 a by an appropriately configured message generated by thesecond UI 240 in response to user input. For example, in response to themessage, the aSC 230 a may ignore messages sent by the first comfortsensor 160, at least for the purposes of controlling the demand unit155. In an optional step 2940, the aSC 230 a controls the demand unit155 in response to the temperature reported by both the first and thesecond comfort sensor 160. In some cases, the aSC 230 a averages bothreported temperatures and controls the demand unit 155 in response tothe computed average. Those skilled in the pertinent art will appreciatethat the method 2900 may be extended in principle to an arbitrarilylarge number of comfort sensors 160 within the limits of the number ofdevices supportable by the system 100. The method ends with a step 2950,from which the operation of the system 100 may continue in any desiredmanner.

In some embodiments, the first comfort sensor 160 is located in anenclosure with a first UI 240, and the second comfort sensor 160 islocated in an enclosure with a second UI 240. The aSC 230 a may beconfigured to control the demand unit 155 in response to the firstcomfort sensor 160 in response to contact by the operator with a touchscreen of the first UI 240. In this case, the UI 240 may be programmedto send an appropriately configured control message to the aSC 230 a inresponse to a single tap of the touch screen, a predetermined number oftaps within a predetermined time interval, or a number of fingerssimultaneously tapped on the touch screen. These examples are presentedwithout limitation and are not exclusive of other combinations oftouches that the UI 240 may be configured to recognize as a command togive priority to the associated comfort sensor 160. In some embodiments,the first UI 240 and/or the second UI 240 are configured to send thecontrol message is response to a command entered via a control menu ofthe UI 240. In some embodiments the UI/G 250 is configured to providethe control message to the aSC 230 a in response to a signal from aremote entity. One aspect of using one of the aforementioned embodimentsor other embodiments within the scope of the disclosure is that a mostrecent UI 240 to be touched by the operator is the UI 240 thateffectively controls the system 100 from the operator's perspective. Insome cases, another UI 240 will provide actual control as a “master” UI240, while the most recently touched UI 240 provides “virtual” controlby sending messages instructing the master UI 240 to control the system100 in a desired manner.

In some embodiments a first UI 240 or a second UI 240 send a message tothe aSC 230 a on the subnet indicating that the first or second UI 240is the last UI 240 to be touched. In this embodiment, the aSC 230 adetermines which is the last UI 240 to be touched and disregards controlmessages from the UI 240 that is not the last to be touched. Thoseskilled in the pertinent art will appreciate that other control schemesare possible to accomplish the desired result of control from the mostrecently touched UI 240.

Accordingly, FIG. 30 presents a method generally designated 3000 ofmanufacturing an HVAC data processing and communication network. Themethod 3000 is described without limitation by referring to the UI 240and the system 100. By way of example without limitation the discussionof the method 3000 includes an aSC 230 a, a first UI 240 and a second UI240 and the demand unit 155, e.g., the furnace 120. The method 3000begins with a step 3010 that may be entered from any appropriateoperational state of the system 100.

In a step 3020, the first UI 240 is configured to broadcast a message onthe data bus 180 indicating that the first UI 240 has been touched. Thefirst UI 240 may detect a touch, e.g., via a touch-sensitive screen. Ina step 3030, the second UI 240 is configured to broadcast a message onthe data bus 180 indicating that the second UI 240 has been touched. Ina step 3040, the aSC 230 a controls the operation of the demand unitconsistent with the control message send by the most recently touched ofthe first UI 240 and the second UI 240.

In one embodiment, the aSC 230 a receives control messages directly fromboth the first and the second UI 240. Each of the first and the secondUI 240 send a message to the aSC 230 a when that UI 240 is touched. TheaSC 230 a is configured to then respond to the UI 240 that last sent themessage indicating it has been touched. In another embodiment, the aSC230 a only responds directly to control messages sent by the first UI240, and the first UI 240 acts a proxy for the second UI 240 when thesecond UI 240 is touched more recently. In this case the second UI 240may send a message to the first UI 240 when the second UI 240 istouched. The first UI 240 then sends control messages to the aSC 230 aconsistent with the control messages received from the second UI 240.The method 3000 ends with a step 3040 from which operation of the systemmay continue in any desired manner.

Without limitation to various methods of operating the system 100, anillustrative example is provided of using the method 3000. An operatoror occupant may enter a first room in which the first UI 240 is located.The operator may touch the touch-sensitive display of the first UI 240.In response, the first UI may send a message to the aSC 230 a indicatingthat the display has been touched. The aSC 230 a determines that thefirst room is occupied, and configures itself to accept messages fromthe first UI 240 related to control the operation of the demand unit 155associated with the aSC 230 a. The aSC 230 a may also configure itselfto disregard messages related to controlling the operation of the demandunit 155 that originate from the second UI 240, which may be located ina second room. Thus, the aSC 230 a controls the operation of the demandunit 155 consistent with a control message sent by the most recentlytouched UI 240. In some cases the first and the second UI 240 may have adifferent control temperature stored therein to which the aSC 230 acontrols to. In other cases, the first and the second UI 240 may beassociated with a different comfort sensor 160. In such cases, the aSC230 a may control the demand unit 155 to maintain the programmedtemperature as measured by the comfort sensor 160 associated with thelast-touched UI 240.

Turning now to FIG. 31, illustrated is an embodiment of an installerdashboard, generally denoted 3100, that is associated with operation ofthe UI 240. The dashboard 3100 may be invoked, e.g., by selecting theservice soft switch 990. The dashboard 3100 may include a number of tabsconfigured to access functionality of particular utility to an installeror otherwise sophisticated operator. In the illustrated embodiment,without limitation, the dashboard 3100 includes an installer test tab3110, an installer/setup tab 3120, an equipment tab 3130, and diagnostictab 3140, and an alert tab 3150. The dashboard 3100 also includes thehelp tab 940 and the home tab 980 as previously described (FIG. 9).Selection of each of the tabs 3110, 3120, 3130, 3140, 3150 may invokes aparticular installer screen. Installer screens may provide functionalityof the UI 240 that is specific to installation or service functions ofthe system 100. Selection of soft switches on the service screens mayinvoke various setup and/or calibration routines, e.g.

FIG. 32 illustrates a screen transition map generally designated 3100that is associated with the tabs 3110, 3120, 3130, 3140, 3150, 940.Installer screens may be configured in any manner that results in, e.g.,convenient or intuitive presentation of installer functions to theoperator. Upon selection of the service soft switch 990, the display 905may present a warning screen 3210. The warning screen 3210 may, forexample, inform the operator that proceeding may provide access tofunctions that may disable the system 100 if performed by unqualifiedoperators. Optionally, access to configuration functions may berestricted by a passcode. Optionally, the warning screen 3210 provides asoft switch, the activation of which returns the display 905 to the homescreen 1080.

In the illustrated embodiment, an installer test screen 3220 may providean option to reset the system 100 into a soft resent or initial power-upstate. Various system-level or device-level tests may be made availableto the operator. An installation and setup screen 3230 may providefunctions useful to configuring the system 100, such as parameter entryand replacement part check. An equipment screen 3240 may provide to theoperator a list of devices available on the data bus 180 and access tofunctions such as independent and dependent parameter display andupdate. A diagnostic screen 3250 may present to the operator a list ofdevices on the data bus 180 and an option to run a diagnostic routine ona selected device. A diagnostic routine may place the selected device ina self-test mode, e.g., and return parameter values reflecting theoutcome of the self-test. An alert screen 3260 may present to theoperator a list of devices on the data bus 180 and a menu of functionsrelated to those devices, such as viewing device-level alerts. A helpscreen 3270 may provide access to information helpful to the operatorregarding installation-related functions, or manufacturer contactinformation, e.g. In some embodiments, the help information iscontext-sensitive. For example, selecting the help tab 940 while usingfunctions of one of the installer test screens may provide help to theoperator related to the installer test functions present on thatinstaller screen. Of course, other screen configurations may be usedwhile remaining within the scope of the disclosure.

Those skilled in the art to which this application relates willappreciate that other and further additions, deletions, substitutionsand modifications may be made to the described embodiments.

1. An HVAC data processing and communication network, comprising: a first zone comprising a first demand unit and a first subnet controller configured to control operation of said first demand unit via a data bus; and a second zone comprising a second demand unit and a second subnet controller configured to control operation of said second demand unit via said data bus, and to communicate with said first subnet controller via said data bus.
 2. The network as recited in claim 1, wherein said first and said second subnet controllers are a same subnet controller.
 3. The network as recited in claim 1, wherein said first and said second demand units are a same demand unit.
 4. The network as recited in claim 1, wherein said first subnet controller is configured to modify operational parameters associated with operation of said second zone.
 5. (canceled)
 6. The network as recited in claim 1, wherein said first zone further comprises a first and a second user interface, and said first and second user interfaces are not located in a same room.
 7. The network as recited in claim 1, wherein said first zone further comprises a first user interface and said second zone further comprises a second user interface, and said first user interface is configured to control operation of said second zone, and said second user interface is configured to control operation of said first zone.
 8. (canceled)
 9. The network as recited in claim 8, wherein said first subnet controller controls an operation of said first demand unit by taking into account environmental data supplied by each of at least two environmental sensors.
 10. (canceled)
 11. A method of manufacturing an HVAC data processing and communication network, comprising: configuring a first subnet controller to control an operation of a first demand unit in a first zone via a data bus; configuring a second subnet controller to control an operation of a second demand unit in a second zone via said data bus; and configuring said first subnet controller to communicate with said second subnet controller via said data bus.
 12. The method as recited in claim 11, wherein said first and said second subnet controllers are a same subnet controller.
 13. The method as recited in claim 11, wherein said first and said second demand units are a same demand unit.
 14. The method as recited in claim 11, further comprising configuring said first subnet controller to modify operational parameters associated with operation of said second zone.
 15. (canceled)
 16. The method as recited in claim 11, wherein said first zone further comprises a first and a second user interface, and said first and second user interfaces are not located in a same room.
 17. The method as recited in claim 11, wherein said first zone further comprises a first user interface and said second zone further comprises a second user interface, and further comprising configuring said first user interface to control operation of said second zone, and configuring said second user interface to control operation of said first zone.
 18. (canceled)
 19. The method as recited in claim 18, wherein said first subnet controller is configured to control an operation of said first demand unit by taking into account environmental data supplied by each of said at least two environmental sensors.
 20. (canceled)
 21. An HVAC data processing and communication network subnet controller, comprising: a physical layer interface configured to couple to a data bus of an HVAC data processing and communications network; and a local controller configured to cooperate with said physical layer interface to publish messages to said data bus configured to operate a first HVAC demand unit in a first zone and a second HVAC demand unit in a second zone.
 22. The subnet controller as recited in claim 21, wherein said first and said second demand units are a same demand unit.
 23. The subnet controller as recited in claim 21, wherein said subnet controller is configured to modify operational parameters associated with operation of said first and said second zone.
 24. The subnet controller as recited in claim 21, further configured to cooperate with a first and a second user interface of said first zone to control said first zone.
 25. The subnet controller as recited in claim 21, wherein said subnet controller is a first subnet controller, said first zone further comprises a first user interface and said second zone further comprises a second user interface, and said first user interface is configured to cooperate with a second user interface to control operation of said second zone.
 26. The subnet controller as recited in claim 21, being housed in a same enclosure as an environmental sensor and a subnet controller, but being addressable independently over said data bus. 